From 1e2619f4b0a8fe9c510c568a545659be4a34edcd Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Wed, 12 May 2010 08:51:26 +0100 Subject: [PATCH] vmx: Change the default Pause-Loop-Exiting "Gap" parameter PLE_Gap controls teh maximum allowable time between executions of PAUSE in a busy loop. Essentially this controls the sensitivity of the processor's busy-loop detection. Changed the default PLE_Gap to 128 for 1. not using odd number like 41 2. getting a little bit more PLE vmexits to improve performance Signed-off-by: Zhai Edwin --- xen/arch/x86/hvm/vmx/vmcs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/arch/x86/hvm/vmx/vmcs.c b/xen/arch/x86/hvm/vmx/vmcs.c index 598ca15633..52594de931 100644 --- a/xen/arch/x86/hvm/vmx/vmcs.c +++ b/xen/arch/x86/hvm/vmx/vmcs.c @@ -53,7 +53,7 @@ boolean_param("unrestricted_guest", opt_unrestricted_guest_enabled); * Time is measured based on a counter that runs at the same rate as the TSC, * refer SDM volume 3b section 21.6.13 & 22.1.3. */ -static unsigned int __read_mostly ple_gap = 41; +static unsigned int __read_mostly ple_gap = 128; integer_param("ple_gap", ple_gap); static unsigned int __read_mostly ple_window = 4096; integer_param("ple_window", ple_window); -- 2.30.2